Aircraft armament system control electronics

ABSTRACT

A computer implemented method for integrating a platform, different stores, and/or carriage racks is implemented in an electronics control system that is communicatively couplable to each of the platform, the different stores, and/or the carriage racks. The computer implemented method includes defining parameters for a plurality of predetermined electrical interfaces for predetermined platforms, stores, and carriage racks, and message sets corresponding thereto, identifying electrical interfaces of the platform, at least one store and/or at least one carriage rack based on the defined parameters, communicating different messages between the platform, the store and/or the carriage rack without affecting an Operational Flight Program (OFP) of the platform, with each communication between the platform, and the store and/or the carriage rack being independent, translating messages between the platform and the store and/or the carriage rack, and controlling operation of the carriage rack and/or the store based on the messages.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/726,524 filed Sep. 4, 2018, and U.S. Provisional Application No. 62/727,621 filed Sep. 6, 2018, which are both hereby incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The invention relates to electronic control systems for armament and platform integration and control.

DESCRIPTION OF THE RELATED ART

Various applications use different launching platforms, such as any land, sea, air, or space vehicle that include a carriage rack for carrying, arming, and releasing a store, such as a munition, pod, fuel tank, or other ordnance. For example, military applications that use land vehicles, aircrafts, surface ships, or underwater vehicles may use stores in executing a mission. Conventional platforms include Operational Flight Programs (OFPs) that are used to perform the necessary functions for integrating and operating the mission store of the platform. For example, the platform can use a messaging protocol to control, monitor, and release the stores on the carriage racks. Adding or modifying a mission store interface typically requires a modification to the OFP which is typically very costly—both from a time and money perspective. Additionally, given the increasing number of different platforms and mission stores, a conventional OFP may be overburdened with managing and handling many different interfaces. Furthermore, modifying the OFP requires obtaining re-certifications for compliance which is a time consuming and cumbersome process.

SUMMARY OF THE INVENTION

A self-contained electronic control module is used to support a wide variety of interfaces for integrating different platforms and mission stores. The electronic control module is configured to receive data from a software configuration file that defines different platform interfaces, store interfaces, carriage rack installations, and message sets, and includes a built-in interface translator for translating messages and data between the components for integration. The translator is implemented in software, firmware, and/or hardware of the electronic control module, including microprocessors and circuitry such as a field-programmable gate array (FPGA), for interface translation between any suitable platform and store. The translator is configured for translation of legacy, i.e. currently existing system, messages and Universal Armament Interface (UAI) messages.

The electronic control module is platform and armament independent such that the module is modular and adaptable to new platforms, armaments and other mission specific parameters through the software configuration file. Advantageously, the electronic control module is operable for integrating different platforms and stores without developing new Operational Flight Program (OFP) software for each potential combination as compared with conventional integration methods, i.e. the electronic control module communicates different messages between the platform, the different stores, and the carriage rack without affecting an OFP of the platform. Operation of the stores and carriage racks, such as arm and release sequences for the stores, is also carried out by the electronic control module in contrast to conventional OFPs that are arranged on the platform and have to be modified to accommodate different stores. Managing the stores using the electronic control module enables the platform OFP to be unburdened. Management of the store operation is enabled by the electronic control module being configured to communicate with the platform and the store on independent and separate busses.

According to an aspect of the invention, a self-contained electronic control module is used for independently communicating with each of a platform, a store, and/or a carriage rack.

According to an aspect of the invention, a self-contained electronic control module includes software, firmware, and/or hardware that enables the module to communicate with each of a platform, a store, and/or a carriage rack.

According to an aspect of the invention, a self-contained electronic control module is configured for integration with an infinite number of different interfaces of platforms, store, and carriage racks.

According to an aspect of the invention, a self-contained electronic control module includes a translator for translating message sets between a platform, a store, and/or a carriage rack including legacy to legacy, UAI to UAI, legacy to UAI, and UAI to legacy. As used herein, “legacy” refers to any currently existing system and legacy to legacy refers to the interface between any existing platform and any existing weapon. Not all platforms carry or interface with all weapons and each weapon has its own unique interface, e.g. communication protocol, timing, and sometimes electrical.

According to an aspect of the invention, a computer implemented method for integrating a platform, different stores, and/or carriage racks is implemented in an electronics control system that is communicatively couplable to each of the platform, the different stores, and/or the carriage racks. The computer implemented method includes defining parameters for a plurality of predetermined electrical interfaces for predetermined platforms, stores, and carriage racks, and message sets that correspond to the predetermined platforms, stores, and carriage racks, identifying electrical interfaces of the platform, at least one store of the different stores and/or at least one carriage rack of the carriage racks to be integrated based on the defined parameters, communicating different messages between the platform, the at least one store and/or the at least one carriage rack without affecting an Operational Flight Program (OFP) of the platform, wherein each communication between the platform, and the at least one store and/or the at least one carriage rack is independent, translating messages between the platform and the at least one store and/or the at least one carriage rack, and controlling operation of the at least one carriage rack and/or the at least one store based on the messages.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes performing a safety check on messages corresponding to the release sequence prior to, up to, and during the release sequence, wherein the safety check is performed by a safety interlock including electronics and an integrated circuit, wherein the electronics, the integrated circuit and the processor are each configured to independently determine and verify a presence of required control signals prior to, up to, and during releasing the at least one store.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes controlling the at least one carriage rack when the at least one carriage rack is a Type I Carriage System or a Type II Carriage System.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes translating message sets that include legacy to legacy, UAI to UAI, legacy to UAI, and UAI to legacy.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes receiving a legacy message from the platform directed to the at least one store, translating the legacy message to a UAI message when the at least one store supports UAI based on the stored data corresponding to the different message sets, and transmitting the UAI message to the at least one store. In some embodiments, similar message translation may be performed in the reverse direction, e.g., UAI message from a store may be translated by the electronics control system to a legacy message and transmitted to a legacy platform, with the messages between the platform and the store being communicated without affecting the OFP of the platform.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes receiving and transmitting different legacy messages between the platform and the at least one store, e.g., when the platform is a legacy platform and the at least one store is a legacy store.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes communicating with at least one of a military standard-1760 interface, an aircraft store-5725 interface, a CAN bus, an RS-422/485 interface, or an Ethernet interface.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes communicating with the identified interface of the at least one store prior to, up to, and during a release sequence of each of the different stores.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes monitoring and storing events occurring during operation of the carriage rack and the at least one store.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes performing telemetry communication and debugging.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes communicating with a military standard-1553B bus.

According to an embodiment of any paragraph(s) of this summary, the method further includes determining a composite launch acceptability region.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes pre-configuring a processor by defining the plurality of predetermined electrical interfaces for different platforms, different stores, different carriage racks, and different message sets that correspond to the different platforms, stores, and carriage racks in a configuration file, and downloading the configuration file in a memory of the electronic control system.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes updating the configuration file to include additional predetermined electrical interfaces.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes simulating the platform and/or the at least one carriage rack for integration with the at least one store prior to operation.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method further includes determining at least one of the interfaces to be a UAI, and performing a UAI certification of at least one of the at least one carriage rack, the at least one stores, or the platform.

According to an embodiment of any paragraph(s) of this summary, the computer implemented method may be executed by a computer-readable medium having processor-executable instructions implementable to execute the computer implemented method.

According to another aspect of the invention, an electronic control module for integrating a platform, different stores, and/or carriage racks includes a processor communicatively couplable to each of the platform, the different stores, and/or the carriage racks, and a memory connected to the processor that contains a set of instructions for identifying a plurality of interfaces for predetermined platforms, stores, and carriage racks, and message sets that correspond to the predetermined platforms, stores, and carriage racks. The processor is configured for executing the set of instructions to identify a configuration of the platform, at least one store of the different stores and/or at least one carriage rack of the carriage racks to be integrated, communicate different messages between the platform, the at least one store and/or the at least one carriage rack without affecting an Operational Flight Program (OFP) of the platform, with each communication between the platform, and the at least one store and/or the at least one carriage rack being independent, translate messages between the platform and the at least one store and/or the at least one carriage rack, and control operation of the at least one carriage rack and/or the at least one store based on the messages. The electronic control module communicates with each of the platform, the at least one store and/or the at least one carriage rack via separate and independent busses.

According to an embodiment of any paragraph(s) of this summary, the electronic control module includes at least one Extended Function Module (EFM) for enabling the electronic control module to perform additional functions.

According to an embodiment of any paragraph(s) of this summary, the electronic control module includes a safety interlock including electronics and an integrated circuit, with the electronics, the integrated circuit and the processor each being configured to independently determine and verify the presence of release consent signals prior to, up to, and during releasing the at least one store.

According to an embodiment of any paragraph(s) of this summary, the electronic control module is used with a munitions rack having a munitions rack structure and multiple munitions ejectors insertable into and securable to the munitions rack structure, wherein the electronic control module integrates a first platform to which the munitions rack is coupled, the munitions rack, and multiple stores coupled to the ejectors and communicates different messages between the first platform, the multiple stores, and the munitions rack without affecting an OFP of the first platform.

To the accomplishment of the foregoing and related ends, the invention comprises the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative embodiments of the invention. These embodiments are indicative, however, of but a few of the various ways in which the principles of the invention may be employed. Other objects, advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF DRAWINGS

The annexed drawings, which are not necessarily to scale, show various aspects of the invention.

FIG. 1 shows a schematic drawing of an electronic control module for integrating a platform and a store.

FIG. 2 shows a schematic drawing of a logical architecture of the electronic control module of FIG. 1.

FIG. 3 shows an oblique view of a first side of a housing for the electronic control module of FIG. 1.

FIG. 4 shows an oblique view of a second side of the housing of FIG. 3.

FIG. 5 shows an oblique view of electronics contained within the housing of FIG. 3.

FIG. 6 shows another oblique view of the electronics contained within the housing of FIG. 3.

FIG. 7 shows a schematic drawing of a wire harness configuration for the housing of FIG. 3 with the platform and the store.

FIG. 8 shows a software architecture for the electronic control module of FIG. 1.

FIG. 9 shows a software architecture for a message manager interface of the electronic control module of FIG. 8.

FIG. 10 shows a software architecture for a safety interlock device of the electronic control module of FIG. 8.

FIG. 11 shows a flowchart of a computer-implemented method for integrating the platform and the store of FIG. 1.

FIG. 12 illustrates an exemplary application or platform in which the electronic control module of FIG. 1 may be used with a manned or unmanned aircraft.

FIG. 13 illustrates another exemplary application or platform in which the electronic control module of FIG. 1 may be used with a helicopter.

FIG. 14 illustrates another exemplary application or platform in which the electronic control module of FIG. 1 may be used with a hypersonic or supersonic vehicle.

FIG. 15 illustrates another exemplary application or platform in which the electronic control module of FIG. 1 may be used with a sea vessel.

FIG. 16 illustrates another exemplary application or platform in which the electronic control module of FIG. 1 may be used with a land vehicle.

DETAILED DESCRIPTION

The principles described herein have particular application in platforms that are suitable for accommodating a carriage rack that carries, arms, and releases a store, such as a munition, pod, fuel tank, or other suitable ordnance. Exemplary platforms include aircraft, space vehicles, land vehicles, ships, underwater vehicles, and other moving platforms. Manned and unmanned platforms may be suitable. The platforms may be used in military applications for executing a particular mission. Many other applications may be suitable.

A computer implemented method for integrating a platform, a store, and a carriage rack is implemented in software, firmware, and/or hardware of an electronic control module, which may also be referred to as a system control electronics (SCE) box, that is communicatively couplable to each of the platform, the store, and the carriage rack and configured to translate messages and other data between the components for integrating the components, such as in executing a particular mission. The electronic control module is a self-contained unit that is configured to support many different interfaces for platforms, mission stores, and carriage racks with minimal or no changes to the software.

The computer implemented method that is executed by the electronic control module includes using a software configuration file to define data or parameters corresponding to a plurality of predetermined electrical interfaces for predetermined platforms, stores, carriage racks, and different message sets that correspond to the platforms, stores, and carriage racks. The software configuration file is used to configure the parameters for a processor of the electronic control module that executes instructions for translating the messages or data between the different components.

The processor may then identify the electrical interfaces of the platform, different stores, and the carriage rack based on the parameters of the configuration file, receive and transmit different messages between the platform, the stores, and the carriage rack, and translate the messages for operation of the stores and the carriage rack. In exemplary configurations, the store or weapon may be the carriage rack. Operation of the stores and/or the carriage rack includes controlling timing, arming, firing, etc. based on the required control signals for a specific weapon and/or platform.

Using the software configuration file, the electronic control module is able to adapt to the interfaces of new platforms, armaments, or other mission specific parameters without having to develop new software for each platform and weapon integration combination. The message translator is coded on at least one circuit board, or a field-programmable gate array (FPGA), and at least one microprocessor that are contained within the electronic control module. In an exemplary embodiment, the electronic control module may include two circuit boards and two microprocessors, with one of the microprocessors being able to be powered off for performing different functions. The processors may be arranged on the same or different electronic boards. The electronic control module may also be used in platform simulation and testing of the store and/or the carriage rack for integrating the store with the platform prior to operation, debugging the software, and/or verifying the component.

Referring first to FIG. 1, a schematic drawing of an electronic control module 20 for integrating a platform 22 and a store 24 is shown. The electronic control module 20 is communicatively coupled between the platform 22 and the store 24 and may be arranged on the platform 22 or the store 24. The store 24 may include any device that is intended for internal or external carriage and mounted on suspension and release equipment of the platform 22, whether or not the item is intended to be separated during operation of the platform 22. The store 24 may be an expendable store that is separated from the platform during operation. Exemplary expendable stores include missiles, rockets, bombs, nuclear weapons, mines, torpedoes, pyrotechnic devices, sonobuoys, signal underwater sound devices, or other similar items. In other applications, the store 24 may be a nonexpendable store that is not separated from the platform during operation. Exemplary nonexpendable stores include tanks (e.g., fuel and spray), line-source disseminators, pods (e.g., refueling, thrust augmentation, gun, electronic attack, data link), multiple racks, targets, cargo drop containers, drones, or other similar items. The electronic control module 20 may be communicatively coupled with a plurality of stores and any suitable number of stores may be used. Using the electronic control module 20 enables integration between any of the aforementioned stores and the platform 22.

The platform 22 and the store 24 each use predetermined messages and interface protocols and the interfaces of the platform 22 and the store 24 may be different. The platform 22 may use military standard-1760 (MIL-STD-1760) precision guided munitions (PGM) mission store and/or a MIL-STD-1553B aircraft interface. The platform interfaces may be referred to as legacy interfaces that refer to any currently existing system. Legacy to legacy refers to the interface between any existing platform and any existing weapon. Not all platforms carry or interface with all weapons and each weapon has its own unique interface (communication protocol, timing, and sometimes electrical). For example, an F-16 aircraft platform may have a standard set of weapons with which it interfaces. The electronic control module 20 may be used to add a legacy weapon and communicate between the existing F-16 OFP and the unique interface on the legacy weapon such that the F-16 OFP is not affected or changed. In contrast, conventional integration required changing the OFP of the platform which is expensive due to the required certifications.

The MIL-STD-1760 PGM mission store may include Guided Bomb Unit-31/32/38 (GBU-31/32/38) Joint Direct Attack Munitions (JDAM), Air-to-Ground Missile-154 (AGM-154) Joint Standoff Weapon (JSOW), Enhanced GBU-24/27/28 (EGBU-24/27/28) Enhanced Paveway™, Cluster Bomb Unit-103 (CBU-103), CBU-104, or CBU-105 Wind Corrected Munitions Dispensers (WCMDs), Air-launched Decoy Missile-160B/C (ADM-160B/C) Miniature Air Launched Decoy (MALD), or AGM-158 Joint Air-to-Surface Stand-Off Missile (JASSM). The message format (i.e., legacy or non-UAI format) for a MIL-STD-1760 PGM mission store can use message structures and definitions conforming to a legacy weapon Interface Control Document (ICD). Many other examples may be suitable.

The store 24 may implement a Universal Armament Interface (UAI) which is a logical or messaging interface allowing for a standardized message structure for various modern weapons and platforms, such as an aircraft. In other exemplary embodiments, the store 24 may be a miniature munition, such as a small diameter bomb which uses an Enhanced Bit Rate-1553 (EBR-1553) protocol. The small munitions may mount to a multi-position carriage system. The electronic control module 20 provides interface translation between the platform 22 and the store 24, and control of the store 24, e.g., during carriage and release or ejection. Exemplary carriage platforms include the bomb release unit 55 (BRU-55) (used by the U.S. Department of the Navy (DoN)) and allows carriage of two smart weapons (e.g., dual weapon up to 1000 lb class) on a single aircraft platform), BRU-33 (dual weapon carriage used by the U.S. Marines), BRU-57 (dual weapon carriage used by the U.S. Air Force (USAF)), munitions armament unit-46 (MAU-46), BRU-71/A, smart bomb rack assembly (SBRA) (including 20 weapons), or heavy stores adapter beam (HSAB) (including 9 weapons for external munitions on USAF B-52H). Many other examples may be suitable.

The electronic control module 20 includes interfaces 26, 28 (e.g., platform interfaces) that are configured for communication with the platform 22. Any number of platform interfaces 26, 28 may be provided on the electronic control module 20. The platform interfaces 26, 28 may include a message interface, such as a legacy interface, and/or a remote terminal, such as a MIL-STD-1553 as an interface on the platform side of the electronic control module 20. One of the interfaces 26, 28 may be configured to receive power 32 from an external power source, i.e. a power source of the platform 22. For example, the power source may be a 28V DC power supply.

The electronic control module 20 further includes interfaces 34, 36 (e.g., platform interfaces) that are configured for communication with at least one store 24. The interfaces 34, 36 and communication between the electronic control module 20 and each store 24 is independent from the platform interfaces and communication between the electronic control module 20 and the platform 22. The interfaces 34, 36 may include bus controller interfaces such as a MIL-STD-1553 bus controller or EBR-1553 bus controller or other interfaces such as RS-422/485, CAN Bus, or Ethernet. The electronic control module 20 includes a built-in interface translator 38 to provide message translation, logical translation, or data manipulation between the platform interfaces and the store interfaces. As shown in FIG. 1, the translator 38 is configured for translating messages 40 a with the platform 22, messages 40 b with one of the stores 24, and messages 40 c with another one of the stores 24.

When the electronic control module 20 receives information from the platform 22, such as a message, the translator 38 is used to translate the information to be sent to and received by the store 24. For example, the platform 22 may include a MIL-STD-1553 (or MIL-STD-1760) bus controller for sending legacy messages to the store 24 and receiving legacy messages from the store 24. Similarly, the store 24 may use UAI messages to the platform and receiving messages from the platform. Thus, the translator 38 may operate as a MIL-STD-1760 (e.g., MIL-STD-1553) remote terminal for the platform and as a MIL-STD-1553 or an EBR-1553 bus controller for the store 24 by providing message layer translation, or logical layer translation, between the legacy interface and the UAI. The translator 38 may convert the legacy message interface on the remote terminal platform side to the UAI message interface on the store bus controller side. The translator 38 may also convert the UAI message interface on the bus controller side to the legacy message interface on the remote terminal platform side. The translator 38 may provide translation for the store 24. For example, the translator 38 may provide MIL-STD-1553B to EBR-1553 translation for the store 24.

Software pertaining to the translator 38 may be coded on a computer readable storage medium, which may be included in an FPGA, and/or coupled to at least one microprocessor. In an exemplary embodiment, the electronic control module 20 may include two circuit boards and two microprocessors. The software may be configured using a data file or a software configuration file 46, such as a mission data file. The mission data file 46 may be arranged in the electronic control module 20 and is used to transport parameters corresponding to specific platforms, stores, carriage racks, and/or mission-specific programming data. Exemplary parameters include powering-up parameters, release parameters, timing parameters, firing parameters, etc. The microprocessors 48, 50 of the electronic control module 20 are then configured to execute a set of instructions for translation based on the data of the mission data file 46. Using the mission data file 46 is advantageous in that the file may be updated to accommodate future configurations of platforms and stores without changing the software executed by the processor.

The translator 38 and the electronic control module 20 enables the store to be integrated onto the platform in various weapon release systems including air-to-air systems, air-to-ground systems, ground-to-ground systems, or ground-to-air systems. In an exemplary application, a UAI store 24 (e.g., SDB-II) may be integrated onto the platform 20 that implements a legacy MIL-STD-1760 messaging interface for an air-to-ground weapon (e.g., a JDAM weapon that is a legacy weapon or an Enhanced Paveway™ that is either a legacy or a UAI weapon). The electronic control module 20 provides a logical interface between the weapon and the aircraft platform. The translator 38 may be implemented in software, firmware, or hardware and runs on the processor 48, 50 to shift and/or recalculate data elements to perform the interface translation. The interface translation may be platform or weapon specific and the translator 38 may adjust to a specific platform based on a received platform identifier message that is determined by the processor 48, 50. Using the message translator enables the electronic control module to communicate different messages between the platform, the different stores, and the carriage rack without affecting or having to change the Operational Flight Program (OFP) of the platform.

In addition to message translation, the electronic control module 20 is also configured to manage and control operation of the carriage rack and the store 24, as compared with conventional methods in which the OFP for operating the store was arranged on the platform. For example, the electronic control module 20 may be configured to perform a monitoring function 50 in which the electronic control module 20 monitors an arm and release status of the store 24. The managing function of the electronic control module 20 is enabled by communicating with the platform 22 and the store 24 on separate and independent busses.

FIG. 2 shows a logical architecture of the electronic control module 20 according to an exemplary embodiment. The electronic control module 20 includes the processor 48, 50, a memory 52 communicatively coupled to the processor 48, 50, and/or an FPGA and a relay set 54 communicatively coupled to the processor 48, 50. An internal power supply 56 is arranged in the electronic control module 20 and connectable to a platform power supply 58. A remote terminal 60 is communicatively coupled between at least one platform multiplexer 62 of the platform and the processor 48, 50. Weapon side bus controllers 64, 66 are also communicatively coupled to the processor 48, 50. One of the bus controllers 64 is communicatively coupled to at least one store 24 a, 24 b and the other bus controller 66 is communicatively coupled to an existing store carriage 68. Operation of each store 24 a, 24 b may be managed independently.

In an exemplary embodiment, the bus controller 64 may be a MIL-STD-1553 bus controller communicatively coupled between the processor 48, 50 and the store 24 a, 24 b, and the bus controller 66 may be a EBR-1553 bus controller communicatively coupled between the processor 48, 50 and the existing store carriage 68. The store carriage 68 may be a single carriage or a dual carriage, or four place carriage, such as a BRU. The existing store carriage 68 may include circuitry 70 such as a joint miniature munitions interface (JMMI)-BRU circuits and stations. Advantageously, the electronic control module 20 is suitable for use with a Type I Carriage System, i.e. a dumb-rack “pass-through” carriage, or a Type II Carriage System in which all of the weapons may be managed and up/down translation with the platform may occur.

The processor 48, 50 is further configured to provide store control 72 and signaling 74 for the stores 24 a, 24 b. For example, the processor 48 may be configured to provide a release command and an arm command to the store 24 a, 24 b based on receiving other data from the platform or the carriage rack. Remote terminals (RTs) 76, 78 may be arranged in the stores 24 a, 24 b. The processor 48, 50 is also configured for communication with a loading interface 80 for the software configuration files 46 (shown in FIG. 1). The loading interface 80 is arranged on the platform multiplexer 62 and may be configured for the mission data files for transporting mission-specific data and configuring the processor 48, 50. Each mission data file may include a capability for a specific weapon or store. A plurality of mission data files may be provided for different weapon capabilities. Accordingly, the electronic control module 20 is configured to download the mission data files and may be configured to convert the mission data files into another mass data transfer (MDT) format. For example, the processor 48, 50 may convert the mission data files into MIL-STD-1760 MDT format. Advantageously, data does not need to be pre-loaded and the data can be transferred on the platform during flight.

The processor 48, 50 is further configured to receive release consent data 82 from the platform, e.g. a pilot's authorization or signal to fire the store 24 a, 24 b, such that the processor 48, 50 may use the release consent data 82 to control a release sequence of the stores 24 a, 24 b. As shown in FIG. 2, the busses between the electronic control module 20 and the other components of the launch system are independent from each other which enables the management and control of the store operation. The electronic control module 20 may include a power return function 84 and an interlock device 86 for providing an interlock function as will be described further below.

The processor 48, 50 may also be configured to perform other functions during operation of the platform and the store. For example, the processor 48, 50 may be configured to determine a composite launch acceptability region. If the processor 48, 50 includes two microcontrollers, one of the microcontrollers may be used to perform this specific function. Telemetry communication may be performed using the processor 48, 50. The telemetry communication may be used for sending flight parameters to the ground. Still another function of the electronic control module 20 may be to perform UAI certification of a weapon interface during integration. The processor 48, 50 may be configured to determine that at least one of the electrical interfaces of the store is UAI based on the known data corresponding to the UAI.

Prior to executing a mission, the electronic control module 20 may also be used in testing and verification of the store and other components. For example, the electronic control module 20 may be coupled to test equipment, such as a control computer to simulate a platform's bus controller and verify the interface translator and legacy interface remote terminal functionality. Legacy to legacy message translation or legacy to UAI message translation may be verified. A bus controller may be coupled to the test equipment to simulate a store carriage's remote terminal and verify the interface translator and the bus controller functionality. The simulator may include a power simulator and an ejector simulator. A computer may be used for debugging and downloading code to the electronic control module 20.

FIGS. 3-7 show a control electronics (SCE) enclosure or box 90 for the electronic control module 20. The SCE box 90 includes a housing 92 for the electronics that includes various external interfaces for connection with different platforms, stores, and carriage racks, such that the SCE box 90 is modular. For example, the SCE box 90 may include at least one store indicator 94 for indicating an arming or firing command for the store. In an exemplary embodiment, the indicator 94 may be a light-emitting diode (LED). A first side of the housing 92 may include an indicator 94 for one of the stores and another side of the housing 92 may include an indicator 96 for another store. The housing 92 may be rectangular in shape or have any other suitable shape that will be dependent on the application, and/or whether the SCE box 90 is arranged on the platform or the weapon. For example, a 1760 interface connector 98 may be provided. Various platform connectors may also be provided on the housing 92. As shown in FIGS. 3 and 4, when installed for operation, the SCE box 90 may include a cover 100 for enclosing the electronics housed within the SCE box 90.

FIGS. 5 and 6 show the electronics housed in the SCE box 90. At least one circuit card 102, or FPGA, and a power relay set 104 is provided. With further reference to FIG. 7 which schematically shows connections to the SCE box 90, the electronics may include any suitable wire harnesses between the SCE box 90 and the platform 22 or the store 24. In an exemplary embodiment, a JMMI/BRU umbilical 106 and a straight 1760 extension 108 may be connected between the SCE box 90 and the store 24. The straight 1760 extension 108 may be connected between the SCE box 90 and the weapon 24, 24 a, 24 b (also shown in FIG. 1). A wire harness 110 may also be connected between the SCE box 90 and a 1760 interface 112 of the platform 22. In an exemplary embodiment, a power supply 114 may be arranged on the platform 22 for supplying remote power to the SCE box 90.

FIGS. 8-10 show exemplary architectures for the computer implemented method performed by the electronic control module 20/SCE box 90 as previously described. As shown in FIG. 8, the architecture includes a Rack OFP 120 that includes the software, the message translator, and a bus controller manager. The architecture further includes a platform interface 122 that handles the store control and status messages to and from the platform, a mission store interface 124 that controls the mission store control and status messages to and from the Rack OFP 120, a rack interface 126 that controls and monitors the power, discretes, and statuses of the hardware for the SCE box 90, a monitoring interface 128 that monitors tasks being performed by the Rack OFP 120, and a usage monitor interface 130 that controls the interfaces for logging and retrieving fault data and events to and from the FPGA and the memory. Using the SCE box 90 enables addition of new platform components or new weapon configurations using the UAI standard without changing or modifying the software. New functions may be added using additional feature sets that are added to existing partitions on the circuit cards or by adding an Extended Function Module 132 for enabling new interfaces. For example, fiber channel or ethernet communications may be enabled.

In an exemplary embodiment, the platform interface 122 may be a MIL-STD-1760 interface with the platform as the bus controller and the Rack OFP 120 as the remote terminal. The platform interface 122 may include other interfaces. The mission store interface 124 may include MIL-STD-1760 with MIL-STD-1553B, with the OFP being the bus controller and the OFP will support an EBR-1553 interface.

With further reference to FIG. 9, the Rack OFP 120 includes a message manager 134 having an interface 136 that interfaces with the platform messaging interface 122. The message manager 134 is configured to route messages based on the message type and handle incoming messages from internal components. The message manager interface 136 may be modular which enables the hardware interface to change without impacting the rest of the software. Using the message manager interface 136 may enable support of other messaging interfaces such as a fiber channel interface 138 or an ethernet interface 140 (or RS-422/485, CAN, etc.). The message manager 134 is configured as a translator including up and down translators 142 a, 142 b for communication between the Rack OFP 120 and the platform. Using the up and down translators 142 a, 142 b enables the message manager 134 to handle additional interfaces without impacting the software. The weapon side of the electronic control module 20 also includes up and down translators. The message manager 134 may be configured to store messages based on the message type and source and route messages to multiple recipients.

Referring now to FIG. 10, an architecture for an interlock device 86 (also shown in FIG. 2) of the electronic control module 20 is shown. The interlock function uses electronics 144, the FPGA 146, and the software executed by the processor to release the store 24. The electronics 144 may use required control signals from the platform 22 and the release consent data 82 to activate the release circuits for the store 24 (shown in FIG. 2). The FPGA 146 and software independently verify that the signals are present before, up to, and during the release sequence for the store 24. The FPGA 146 may also verify an ejector status. If the electronic signals are lost at any point during the release sequence, the release sequence may be halted or aborted by the electronic control module 20. The software may be used to perform safety checks on the hardware for the power supply, the release consent, and the release mechanism or ejector. Using the architecture is advantageous in providing a three-way safety check. Accordingly, arming is able to be performed immediately before launch as compared with conventional systems which only enable arming to be performed on the ground. Using the electronic control module 20 is advantageous in that the required control signals may be different for each weapon or store such that the electronic control module 20 may control any weapon or store.

Referring now to FIG. 11, a flowchart illustrating a computer implemented method 160 for integrating a platform, a store, and a carriage rack is shown. The method 160 may be implemented in software, firmware, and/or hardware of the electronic control module 20/SCE box 90 as described herein. Step 162 of the method includes defining the parameters for a plurality of predetermined electrical interfaces for different platforms, different stores, different carriage racks, and different message sets that correspond to the different platforms, stores, and carriage racks. Step 162 may include using a configuration file. Step 164 of the method 160 includes identifying electrical interfaces of the platform, the store, and the carriage rack based on the defined parameters. Step 164 may include using a processor of the electronic control module described herein that has an application or software that is pre-configured by the configuration file.

Step 166 of the method 160 includes receiving and transmitting different messages between the platform, the store, and the carriage rack. Communication may be performed by the processor and the communication with each of the platform, the store, and the carriage rack is independent relative to communication with another one of the platform, the store, and the carriage rack. Step 168 of the method 160 includes translating messages, if necessary, between the platform and the store. Step 168 may include using a built-in translator of the electronic control module. Step 170 of the method 160 includes controlling operation of the carriage rack and the store, such as release operations.

FIG. 12-16 show exemplary applications including different platforms suitable for use with the electronic control module 20. FIG. 12 shows an aircraft 172 which may be a military aircraft or commercial aircraft, manned or unmanned, FIG. 13 shows a helicopter 174, FIG. 14 shows a hypersonic or supersonic vehicle 176, FIG. 15 shows a naval vessel 178, and FIG. 16 shows a land vehicle 180. Additionally, the electronic control module 20 may be arranged in an underwater vehicle such as a submarine for releasing mini-submarines or underwater drones. In still other exemplary applications, a land vehicle, such as a truck or military vehicle, may include the electronic control module 20.

Various techniques described herein may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), digital versatile disc (DVD), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry may include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium may be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

The functional unit described in this specification has been labeled as a module which may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. The module may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. The executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

A module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

Although the invention has been shown and described with respect to a certain preferred embodiment or embodiments, it is obvious that equivalent alterations and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings. In particular regard to the various functions performed by the above described elements (components, assemblies, devices, compositions, etc.), the terms (including a reference to a “means”) used to describe such elements are intended to correspond, unless otherwise indicated, to any element which performs the specified function of the described element (i.e., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary embodiment or embodiments of the invention. In addition, while a particular feature of the invention may have been described above with respect to only one or more of several illustrated embodiments, such feature may be combined with one or more other features of the other embodiments, as may be desired and advantageous for any given or particular application. 

1. A computer implemented method for integrating a platform, different stores, and/or carriage racks, wherein the computer implemented method is implemented in an electronics control system that is communicatively couplable to each of the platform, the different stores, and/or the carriage racks, the computer implemented method comprising: defining parameters for a plurality of predetermined electrical interfaces for predetermined platforms, stores, and carriage racks, and message sets that correspond to the predetermined platforms, stores, and carriage racks; identifying electrical interfaces of the platform, at least one store of the different stores and/or at least one carriage rack of the carriage racks to be integrated based on the defined parameters; communicating different messages between the platform, the at least one store and/or the at least one carriage rack without affecting an Operational Flight Program (OFP) of the platform, wherein each communication between the platform, and the at least one store and/or the at least one carriage rack is independent; translating messages between the platform and the at least one store and/or the at least one carriage rack; and controlling operation of the at least one carriage rack and/or the at least one store based on the messages.
 2. The computer implemented method of claim 1 further comprising performing a safety check on messages corresponding to the release sequence prior to, up to, and during the release sequence, wherein the safety check is performed by a safety interlock including electronics and an integrated circuit, wherein the electronics, the integrated circuit and the processor are each configured to independently determine and verify a presence of required control signals prior to, up to, and during releasing the at least one store.
 3. The computer implemented method of claim 1 further comprising controlling the at least one carriage rack when the at least one carriage rack is a Type I Carriage System or a Type II Carriage System.
 4. The computer implemented method of claim 1, wherein translating the messages comprises translating message sets that include legacy to legacy, Universal Armament Interface (UAI) to UAI, legacy to UAI, and UAI to legacy.
 5. The computer implemented method of claim 4 further comprising at least one of: receiving a legacy message from the platform directed to the at least one store, translating the legacy message to a UAI message when the at least one store supports UAI based on the stored data corresponding to the different message sets, and transmitting the UAI message to the at least one store; and receiving a UAI message from the at least one store directed to the platform, translating the UAI message to a legacy message based on the stored data corresponding to the different message sets, and transmitting the legacy message to the platform.
 6. The computer implemented method of claim 1 further comprising receiving and transmitting different legacy messages between the platform and the at least one store.
 7. The computer implemented method of claim 1 further comprising communicating with at least one of a military standard-1760 interface, an aircraft store-5725 interface, a CAN bus, an RS-422/485 interface, or an Ethernet interface.
 8. The computer implemented method of claim 1 further comprising communicating with the identified interface of the at least one store prior to, up to, and during a release sequence of the at least one store.
 9. The computer implemented method of claim 1 further comprising monitoring and storing events occurring during operation of the at least one carriage rack and/or the at least one store.
 10. The computer implemented method of claim 1 further comprising performing telemetry communication and debugging.
 11. The computer implemented method of claim 1 further comprising determining a composite launch acceptability region.
 12. The computer implemented method of claim 1 further comprising: pre-configuring a processor by defining the plurality of predetermined electrical interfaces for different platforms, different stores, different carriage racks, and different message sets that correspond to the different platforms, stores, and carriage racks in a configuration file; and downloading the configuration file in a memory of the electronics control system.
 13. The computer implemented method of claim 12 further comprising updating the configuration file to include additional predetermined electrical interfaces.
 14. The computer implemented method of claim 1 further comprising simulating the platform and/or the at least one carriage rack for integration with the at least one store prior to operation.
 15. The computer implemented method of claim 1 further comprising: determining at least one of the interfaces to be a UAI; and performing a UAI certification of at least one of the at least one carriage rack, the at least one store, and the platform.
 16. A computer-readable medium having processor-executable instructions implementable to execute the computer implemented method according to claim
 1. 17. An electronic control module for integrating a platform, different stores, and/or carriage racks, the electronic control module comprising: a processor communicatively couplable to each of the platform, the different stores, and/or the carriage racks; and a memory connected to the processor, wherein the memory contains a set of instructions for identifying a plurality of interfaces for predetermined platforms, stores, and carriage racks, and message sets that correspond to the predetermined platforms, stores, and carriage racks, wherein the processor is configured for executing the set of instructions to: identify a configuration of the platform, at least one store of the different stores and/or at least one carriage rack of the carriage racks to be integrated; communicate different messages between the platform, the at least one store and/or the at least one carriage rack without affecting an Operational Flight Program (OFP) of the platform, wherein each communication between the platform, and the at least one store and/or the at least one carriage rack is independent; translate messages between the platform and the at least one store and/or the at least one carriage rack; and control operation of the at least one carriage rack and/or the at least one store based on the messages, wherein the electronic control module communicates with each of the platform, the at least one store and/or the at least one carriage rack via separate and independent busses.
 18. The electronic control module of claim 17, wherein the identifying a plurality of interfaces for predetermined platforms, stores, and carriage racks, and message sets that correspond to the predetermined platforms, stores, and carriage racks is based on parameters stored in a configuration file accessible by the electronic control module; and wherein the electronic control module further comprises at least one Extended Function Module (EFM) for enabling the electronic control module to perform additional functions.
 19. The electronic control module of claim 17 further comprising a safety interlock including electronics and an integrated circuit, wherein the electronics, the integrated circuit and the processor are each configured to independently determine and verify a presence of required control signals prior to, up to, and during releasing the at least one store.
 20. The electronic control module of claim 17, wherein the electronic control module is used with a munitions rack having a munitions rack structure and multiple munitions ejectors insertable into and securable to the munitions rack structure, wherein the electronic control module integrates a first platform to which the munitions rack is coupled, the munitions rack, and multiple stores coupled to the ejectors and communicates different messages between the first platform, the multiple stores, and the munitions rack without affecting an OFP of the first platform. 